feat: add 14-day minimum release age for external dependencies #1135
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add minimumReleaseAge policy to wait 14 days before updating external packages, providing time for potential issues to be discovered and fixed before adoption. This helps protect against supply chain attacks like the recent npm debug and chalk package compromises. Related discussion: https://cq-dev.slack.com/archives/C01UB5Y1YQ7/p1757493562576669 Reference: https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]> Signed-off-by: Lars Trieloff <[email protected]>
tripodsan
approved these changes
Sep 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
minimumReleaseAge: "14 days"policy to external dependency update rules in Renovate configurationContext
This change adds an additional security layer in response to recent supply chain attacks on npm packages. By waiting 14 days before considering updates, we allow time for the community to identify and report compromised packages.
Related discussion: https://cq-dev.slack.com/archives/C01UB5Y1YQ7/p1757493562576669
Reference article: https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised
Test plan
🤖 Generated with Claude Code